Skip to content

Conversation

@hamishmack
Copy link
Collaborator

These components may depend on the library component of the package however plan.json does not include that dependency (since cabal will build all the components at once). This fix adds the library component as a dependency of the other components.

These components may depend on the `library` component of the package however `plan.json` does not include that dependency (since cabal will build all the components at once).  This fix adds the library component as a dependency of the other components.
Copy link
Member

@andreabedini andreabedini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT

hamishmack added a commit that referenced this pull request Oct 8, 2024
This is an alternative to #2257 that is probably closer to the `cabal-install` behaviour.

It also has the advantage of removing the special case for `cabal-doctest`.
@hamishmack hamishmack merged commit 1cc7d4b into master Oct 9, 2024
29 of 31 checks passed
pranaysashank pushed a commit to kronor-io/haskell.nix that referenced this pull request Jan 18, 2025
* Fix components in `build-type: Custom` packages

These components may depend on the `library` component of the package however `plan.json` does not include that dependency (since cabal will build all the components at once).  This fix adds the library component as a dependency of the other components.

* ifdLevel 1

* Add comment and only include library if there is one.

* ifdLevel 2

* ifdLevel 3

* Fix broken test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants